Managing data structures in a plurality of memory devices that are indicated to demote after initialization of the data structures

ABSTRACT

Provided are computer program product, system, and method for managing data structures in a plurality of memory devices that are indicated to demote after initialization of the data structures. Indication is made to data structures to demote after initialization from a first level memory device to a second level memory device. The first level memory device has lower latency than the second level memory device. In response to completing initialization of the data structures in the first level memory device, the data structures indicated to demote after initialization are copied from the first level memory device to the second level memory device and removing the data structures indicate to move after initialization from the first level memory device.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a computer program product, system, andmethod for managing data structures in a plurality of memory devicesthat are indicated to demote after initialization of the datastructures.

2. Description of the Related Art

A storage class memory (SCM) system utilizes low latency Dynamic RandomAccess Memory (DRAM) and one or more higher latency flash NAND memorydevices, which are less expensive than DRAM, to provide greater storagein the memory or cache at a lower cost by using higher latency, lowercost NAND devices. SCM allows system memory to be expanded with fastaccess non-volatile memory NAND devices.

Flash memory devices have less endurance than DRAM as there are alimited number of erase cycles for flash bit cells, far less so than forDRAM cells. One technique in the prior art to reduce wear on the flashmemory devices is to use wear leveling techniques that distribute writesacross multiple flash memory cells in the same or different device toavoid overuse of specific flash memory cells.

There is a need in the art for improved techniques for managing thestorage of data in the multiple memory devices in a memory subsystem,such as an SCM system.

SUMMARY

Provided are computer program product, system, and method for managingdata structures in a plurality of memory devices that are indicated todemote after initialization of the data structures. Indication is madeto data structures to demote after initialization from a first levelmemory device to a second level memory device. The first level memorydevice has lower latency than the second level memory device. Inresponse to completing initialization of the data structures in thefirst level memory device, the data structures indicated to demote afterinitialization are copied from the first level memory device to thesecond level memory device and removing the data structures indicate tomove after initialization from the first level memory device.

With the above embodiment, very infrequently accessed data structuresmay be moved to a lower level memory device for continual storagebecause they are infrequently accessed and read access can be servicedfrom the lower level memory device. However, if there is a need to writeto the data structure indicated as demote after initialization, then thedata structure may be moved into the first level memory device for oneor more write operations to that data structure. When the writeoperations are completed, the data structure may be demoted from thefirst level memory device and moved to a lower level memory devicebecause the data structure will unlikely be write accessed for asubstantial time.

In a further embodiment, access counts are maintained for the datastructures stored in the first level memory device that are notindicated to demote after initialization, wherein access counts are notmaintained for data structures indicated to demote after initialization.

With the above embodiment, access counts are not needed for datastructures that are automatically demoted after being updated orinitialized because they are vacated from the first level memory deviceafter being used without regard to access counts.

In a further embodiment, the access counts are used to select datastructures to remove from the first level memory device and retain inthe second level memory device to free space in the first level memorydevice. The access counts are used to determine whether to removeaccessed data structures from the second level memory device.

With the above embodiment, using access counts to determine whether tostore data structures in a low latency or high latency storage allowsimproves system performance by placing the high access count data in lowlatency storage to optimize system performance and place low accesscount data in higher latency storage, which will have less effect onsystem performance because low access count data is less frequentlyaccessed.

In a further embodiment, an update is received to a data structureindicated to demote after initialization. The data structure to updateis copied from the second level memory device to the first level memorydevice to update. The updated data structure is copied from the firstlevel memory device to the second level memory device and the updateddata structure is deleted from the first level memory device.

With the above embodiment, system performance is improved by moving theupdated data structure being indicated to demote after initialization tothe lower latency memory device to perform the update. The datastructure is then deleted from the first level memory device after beingupdated because it is unlikely to be accessed given that a datastructure indicated to demote after initialization is accessed veryinfrequently.

Further provided are a computer program product, system, and method formanaging data in a plurality of memory devices in a computing system. Anupdate is received to a data structure indicated to demote from a firstlevel memory device. The data structure to update is copied from asecond level memory device to the first level memory device to update.The first level memory device has lower latency than the second levelmemory device. The updated data structure is copied from the first levelmemory device to the second level memory device and deleted from thefirst level memory device in response to updating the data structure.

With the above embodiment, system performance is improved by moving theupdated data structure being indicated to demote to the lower latencymemory device to perform the update, and then deleted from the firstlevel memory device after being updated because it is unlikely to beaccessed given that a data structure indicated to demote afterinitialization is accessed very infrequently. Removing an infrequentlyaccessed data structure from the low latency device to a higher latencydevice for storage improves system performance by maximizing free spacein the low latency device to be available for more frequently accesseddata structures.

In a further embodiment, the update to the data structure is to at leastone field in the data structure to update that is less than all thefields in the data structure. Copying the data structure comprisescopying only the at least one field to update from the data structure tothe first level memory device, wherein the copying the updated datastructure comprises copying the updated at least one field from thefirst level memory device to the second level memory device and deletingthe updated at least one field from the first level memory device.

With the above embodiment, the low latency first level memory space isfurther conserved and optimized by only copying fields to update fromthe data structures in the second level memory device to the first levelmemory device to update.

In a further embodiment, the data structure to update is in the secondlevel memory device. A determination is whether the update comprises anupdate event of a plurality of predefined update events. The datastructures are copied to update to the first level memory device inresponse to determining the update comprises the update event. Aplurality of writes to the data structure are performed as part of theupdate event. The data structure updated as part of the update event arecopied from the first level memory device to the second level memorydevice and deleting the updated data structure from the first levelmemory device in response to completing the writes for the update event.

With the above embodiment, data structures that are to be demoted afterbeing updated or initialized are copied to the first level memory deviceif they are going to be subject to a burst of writes, although generallyinfrequently accessed. Such data structures may be periodically stagedinto the first level memory device for a burst of writes as part ofoperations to update system configuration files. Because suchconfiguration files are very infrequently updated, after the updateevent, the system data structure may be moved back to a lower levelmemory device for storage and access. This frees up space in the fasteraccess first level memory device for other more frequently accesseddata.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a computing environment with amemory subsystem having a plurality of memory devices.

FIG. 2 illustrates an embodiment of data structure information to managestorage of data structures in the memory devices.

FIG. 3 illustrates an embodiment of operations to perform systeminitialization to generate initial system data structures.

FIG. 4 illustrates an embodiment of operations to process an accessrequest for a single copy case where only a single copy of datastructures are stored throughout the memory subsystem.

FIG. 5 illustrates an embodiment of operations to perform memorymanagement operations to free space in a first level memory device for asingle copy case where only a single copy of the data structures arestored throughout the memory subsystem.

FIG. 6 illustrates an embodiment of operations to process an accessrequest for a multiple copy case where multiple copies of datastructures are stored throughout the memory subsystem.

FIG. 7 illustrates an embodiment of operations to perform memorymanagement operations to free space in a first level memory device for amultiple copy case where multiple copies of the data structures arestored throughout the memory subsystem.

FIG. 8 illustrates an embodiment of operations to process an accessrequest for a multiple copy case where multiple copies of datastructures with separate update and read counts are stored throughoutthe memory subsystem.

FIG. 9 illustrates an embodiment of operations to perform memorymanagement operations to free space in a first level memory device for amultiple copy case where multiple copies of the data structures withseparate update and read counts are stored throughout the memorysubsystem.

FIG. 10 illustrates an embodiment of operations to perform a systeminitialization and generate data structures in a memory subsystem with aplurality of memory devices.

FIG. 11 illustrates an embodiment of operations to process access todata structures that are demoted after initialization in a memorysubsystem of a plurality of memory devices.

FIG. 12 illustrates a computing environment in which the components ofFIG. 1 may be implemented.

DETAILED DESCRIPTION

System control structures used to define logical devices in thecomputing system may be maintained in the main DRAM memory. However, asthe DRAM gets to an almost full level, time consuming memory managementprocesses are used to move the data structures in DRAM to a lower levelstorage, such as a higher latency NAND type flash memory or diskstorage.

Described embodiments provide improved computer technology for managingdata structures in a memory subsystem comprised of a plurality ofdifferent level memory devices having different characteristics, such asa lowest latency first level memory device, e.g., DRAM, and differenthigher latency, less expensive lower level memory devices, e.g., NANDflash memory. With described embodiments, access counts are used todetermine when to move data structures from the first level memorydevice to a lower level memory device having higher latency. The accesscounts may also be used to determine whether to maintain multiple copiesof a data structure in the first level memory device and a lower levelmemory device based on access thresholds maintained for different lowerlevel memory devices to match placement of the data structures in lowerlevel memory devices having suitable endurance profiles, e.g., number oferase cycles, to the access count profile of the data structures.

In further embodiments, the access count may be used to determinewhether to maintain multiple copies of a data structure in multiple ofthe memory devices when accessing a data structure or just leave in thefirst level memory device. Data structures that are less frequentlyaccessed than most frequently updated data structures may be indicatedas swappable to allow for storage in lower level memory devices havinghigher latency, whereas the most frequently accessed data structures maynot be swappable and remain in the lowest latency first level memorydevice.

Yet further, the access count may comprise separate read and updatecounts to use to determine whether to move less frequently updated datastructures to lower level memory devices. Further, there may be moreexpensive of the lower level memory devices having a higher endurance,such as allowing for more erase cycles, and only the highest accesscount data structures are placed in those lower level memory deviceshaving greater endurance and those data structures having a lower updatecount may be stored in less expensive lower level memory devices thathave lower endurance, e.g., allow for fewer erase cycles. This allowsfor matching of data structures by update count with lower level memorydevices based on the endurances of the lower level memory devices tooptimize placement of the data structures among the lower level memorydevices.

FIG. 1 illustrates an embodiment of a computing environment. A pluralityof hosts 102 may submit Input/Output (I/O) requests to a storagecontroller 104 over a network 106 to access data at volumes 108 (e.g.,Logical Unit Numbers, Logical Devices, Logical Subsystems, etc.) in astorage 110. The storage controller 104 includes one or more processors112 and a memory subsystem, such as a storage class memory (SCM) memorysystem, having a virtual memory manager 114 to manage the placement oftracks in one of a plurality memory devices, such as a first levelmemory device 116 ₁, a second level memory device 116 ₂, through an nthlevel memory device 116 _(n). The virtual memory manager 114 maintainsdata structure information 200 having information on data structures 118₁, 118 ₂, 118 ₃, such as system data structures or objects, generated byan operating system during system initialization, that the virtualmemory manager 114 processes to determine one or more level memorydevices 116 ₁ . . . 116 _(n) on which to store system and other datastructures. The virtual memory manager 114 may also maintain addresstranslation tables to provide translation services and map tracks in thevolumes 108 to physical or logical locations in the memory devices 116 ₁. . . 116 _(n). The virtual memory manager 114 may further includealgorithms to perform wear leveling to distribute write operations todifferent memory devices 116 ₂ . . . 116 _(n) and different locationswithin the memory devices, such as solid state storage devices (SSDs) orflash memory, that have a limited number of erase cycles to increase thelife span of these lower level memory devices 116 ₁ . . . 116 _(n). Incertain embodiments, the memory subsystem comprising the virtual memorymanager 114 and level memory devices 116 ₁ . . . 116 _(n) may functionas a cache for the storage controller 104 or other computing device.

The processor 112, virtual memory manager 114, and memory devices 116 ₁. . . 116 _(n) may communicate over one or more bus interfaces 120.Further, the virtual memory manager 114 may communicate over differenttypes and separate bus and device interfaces for different of the memorydevices 116 ₁ . . . 116 _(n). For instance, a local memory interface maybe used to communicate with the first level memory device 116 ₁, such asfor a DRAM, and a storage device interface may be used to communicatewith the lower level memory devices 116 ₂ . . . 116 _(n), such asNon-Volatile Memory Express (NVME) to communicate with flash memory andSSDs.

In one embodiment, the first level memory device 116 ₁ may comprise ahigh cost and very low latency device such as a Dynamic Random AccessMemory (DRAM) or Static Random Access Memory (SRAM), and the lower levelmemory devices 116 ₁ . . . 116 _(n) may comprise less expensive andhigher latency and higher capacity storage devices such as non-volatilerandom access memory (NVRAM), including Magnetoresistive Random AccessMemory (MRAM), Phase Change Memory (PCM), Resistive Random Access Memory(RRAM), spin transfer torque memory (STM-RAM), conductive bridging RAM(CBRAM), NAND memory devices, such as flash memory and solid statedrives (SSDs), etc. In one embodiment, the lower level memory devices116 ₂ . . . 116 _(n) may have different endurance profiles withdifferent number of available erase cycles, such that higher level ofthe memory devices 116 ₂ . . . 116 _(n) allow for a greater number oferase cycles, i.e., greater endurance, than the lower level of thememory devices 116 ₂ . . . 116 _(n). For instance, lower level memorydevice 116 _(i) may have a greater endurance, i.e., higher number oferase cycles, than lower level memory device 116 _(j), where i<j. Theremay be one or more lower level memory devices 116 _(i).

The virtual memory manager 114 may comprise a separate processing orhardware device implemented as microcode or firmware in hardware devicesin the storage controller 104, such as in Application SpecificIntegrated Circuits (ASICs). Alternatively, the virtual memory manager114 may comprise a system having a processor executing code loaded intoa memory device. Still further, the virtual memory manager 114 may beimplemented as code loaded into the first level memory device 116 ₁ andexecuted by the processor 112.

The storage 110 may comprise one or more storage devices known in theart, such as a solid state storage device (SSD), magnetic hard diskdrive, optical disk, tape, etc. The storage devices may further beconfigured into an array of devices, such as Just a Bunch of Disks(JBOD), Direct Access Storage Device (DASD), Redundant Array ofIndependent Disks (RAID) array, virtualization device, etc. Further, thestorage devices may comprise heterogeneous storage devices fromdifferent vendors or from the same vendor.

The network 106 may comprise a Storage Area Network (SAN), a Local AreaNetwork (LAN), a Wide Area Network (WAN), the Internet, and Intranet,etc.

Alternatively, the hosts 102 may connect to the storage controller 104over a bus interface, such as a Peripheral Component Interconnect (PCI)bus interface and other interfaces known in the art.

FIG. 2 illustrates an embodiment of an instance of the data structureinformation 200 _(i) for a data structure including a data structureidentifier (ID) 202, such as a file or object name; a swappable flag 204indicating whether the data structure 202 may be regularly moved betweenthe first level memory device 116 ₁ and the lower level memory devices116 ₂ . . . 116 _(n); an update count 206 indicating a number of timesthe data structure 202 has been updated within a measurement period; aread count 208 indicating a number of times the data structure 202 hasbeen read a measurement period; a demote after initialization flag 210indicating whether the data structure 202 is to be immediately demotedafter being generated in the first level memory device 116 ₁; and adevice pointer 212 indicating the level memory device 116 ₁ . . . 116_(n) in which the data structure 202 is currently stored.

In one embodiment, the swappable flag 204 and the demote afterinitialization flag 210 may be set by the operating system developer oradministrator based on the estimated frequency the data structures willbe accessed. For instance, data structures that are the most frequentlyupdated or accessed may be marked as swappable to always retain in thefastest first level memory device 116 ₁. Data structures 118 ₁, 118 ₂,118 ₃ that are less frequently accessed may be occasionally swapped tothe lower level memory devices 116 ₂ . . . 116 _(n) to free space in thefirst level memory device 116 ₁.

The update count 206 may be used to select a lower level memory device116 _(i) on which to store a data structure to match with the endurance,or available erase cycles. For instance, more frequently accessed datastructures, those with a higher update count 206, may be placed on alower level memory device 116 _(i) having a higher endurance. In thisway, each of the lower level memory devices 116 ₂ . . . 116 _(n) may beassociated with a range of update counts. In an alternative embodiment,there may be just one access count for reads and/or writes used todetermine when to swap a data structure out of the first level memorydevice 116 ₁ and to select a lower level memory device 116 _(i) to storethe swapped data structure.

Data structure information 200 _(i) indicated as not swappable 204 maynot maintain access counts 206, 208 because such data structures are notmanaged between the memory devices based on their access.

The demote after initialization flag 210 may be set for data structuresalso indicated as not swappable 204 that are static and rarely, butsometimes changed. In such case, such very infrequently accessed datastructures may be moved to a lower level memory device 116 _(i) forcontinual storage because there will very infrequent write access andread access can be serviced from the lower level memory device 116 _(i).However, if there is a need to write to the data structure indicated asdemote after initialization 210, then the data structure may be movedinto the first level memory device 116 ₁ for one or more writeoperations to that data structure. When the write operations arecompleted, the data structure may be demoted from the first level memorydevice 116 ₁ and moved to a lower level memory device 116 _(i) becausethe data structure will unlikely be write accessed for a substantialtime.

In one embodiment, the data structures managed by the virtual memorymanager 114 may comprise data structures generated during systeminitialization or initial microcode load (IML), and include structuresproviding configuration information for hardware devices and logicaldevices, paths and subsystems, device characteristics, and settings. Inalternative embodiments, the data structures may be generated byapplications.

In certain embodiments, periodically, the virtual memory manager 114 maydecrement the access counts, such as update 206 and read 208 counts, toreduce weighting of accesses over time. This provides that the strengthof the access counts are time sensitive, and decay over time.

FIG. 3 illustrates an embodiment of operations performed for systeminitialization of the storage controller 100 by an operating system ofthe storage controller 100, which may be maintained in the first levelmemory device 116 ₁ and the virtual memory manager 114. Upon initiatingsystem initialization (at block 300), the system data structures aregenerated (at block 302) and stored in the first level memory device 116₁. For each of the generated data structures indicated as demote afterinitialization 210, the generated data structures are copied (at block304) to the lowest level memory device (e.g., third level) and removefrom the first level memory device 116 ₁.

FIG. 4 illustrates an embodiment of operations performed by the virtualmemory manager 114 to process an access request, such as read or write,for a single copy case where only one copy of a data structure 118 _(i)is maintained in the memory devices 116 ₁ . . . 116 _(n). Uponprocessing (at block 400) the access request, if (at block 402) theaccessed data structure 118 _(i) is not swappable 204, control proceedsto FIG. 11 for processing as a non-swappable data structure. If (atblock 402) the swappable flag 204 in the data structure information 200_(i) for the accessed data structure 118 _(i) indicates the datastructure 118 _(i) is swappable, then the access count is incremented(at block 406). In the embodiment of FIGS. 4 and 5 , there may be justone access count for read and/or write accesses.

If (at block 408) the accessed data structure 118 _(i) is in the firstlevel memory device 116 ₁, then the access request is performed (atblock 410) at the first level memory device 116 ₁. If the data structure118 _(i) is not in the first level memory device 116 ₁, then the virtualmemory manager 114 copies (at block 412) the data structure 118 _(i)from a lower level memory device 116 _(i) to the first level memorydevice 116 ₁, removes (at block 414) the data structure 118 _(i) fromthe lower level memory device 116 _(i), and updates the device pointer212 to indicate the first level memory device 116 ₁.

With the embodiment of FIG. 4 , the virtual memory manager 114 maintainsa single copy of the data structures in one of the memory devices 116_(i), and moves a swappable data structure from a lower level memorydevice 116 _(i) to the first level memory device 116 ₁ when accessed.

FIG. 5 illustrates an embodiment of operations performed by the virtualmemory manager 114 to free space in the first level memory device 116 ₁in the case where a single copy of the data structure 118 _(i) ismaintained in one of the memory devices 116 _(i). Upon initiating (atblock 500) memory management, if (at block 502) the amount of free spacein the first level memory device 116 ₁ is above a memory threshold, thencontrol ends. If (at block 502) the amount of free space is below thememory threshold, then the virtual memory manager 114 selects (at block504) data structures 118 _(i) in the first level memory device 116 ₁indicated as swappable having lowest access counts that satisfy a freespace amount. The selected data structures are copied (at block 506) toone of the lower level memory devices 116 _(i), removed from the firstlevel memory device 116 ₁, and the device pointers 212 for the moveddata structures are updated to point to the lower level memory devices116 _(i) to which they are added.

In one embodiment, the access counts for the selected data structuresmay be used to determine the lower level memory device in which the datastructures are stored. If the lower level memory devices 116 _(i) areordered according to their endurance in terms of erasable cycles, withthe lower numbered devices having a higher endurance than the highernumber devices, e.g., memory device 116 ₂ has a greater endurance thanmemory device 116 ₃, then a data structure is placed in the memorydevice 116 _(i) having a lowest level threshold exceeding the datastructure access count.

With the embodiment of FIG. 5 , to free space in the first level memorydevice 116 ₁, the virtual memory manager 114 considers data structureshaving a lowest access count, because such data structures are lessfrequently updated and accessed and most suitable for storage in a lowerlevel memory device 116 ₂ . . . 116 _(n).

FIG. 6 illustrates an embodiment of operations performed by the virtualmemory manager 114 to process an access request where multiple copies ofa data structure 118 _(i) are maintained in multiple of the memorydevices 116 ₁ . . . 116 _(n). With the embodiment of FIGS. 6 and 7 thereis one access count comprising update 206 and/or read 208 counts. Uponprocessing (at block 600) the access request, if (at block 602) theaccessed data structure 118 _(i) is not swappable 204, control proceedsto FIG. 11 for processing as a non-swappable data structure. If (atblock 602) the swappable flag 204 in the data structure information 200_(i) for the accessed data structure 118 _(i) indicates the datastructure 118 _(i) is swappable, then the access count is incremented(at block 606).

If (at block 608) the accessed data structure 118 _(i) is in the firstlevel memory device 116 ₁, then the access request is performed (atblock 610) at the first level memory device 116 ₁. If the data structure118 _(i) is not in the first level memory device 116 ₁, then the virtualmemory manager 114 copies (at block 612) the data structure 118 _(i)from a lower level memory device 116 _(i) to the first level memorydevice 116 ₁ and updates (at block 614) the device pointer 212 toindicate the first level memory device 116 ₁. If (at block 616) theaccess request is an update, the copies of the data structures in one ormore memory devices are updated (at block 616).

The virtual memory manager 114 determines (at block 618) a lower levelmemory device 116 _(j) having a lowest level threshold exceeding thedata structure 118 _(i) access count, which is the memory device havingan endurance most suited for the access count of the selected datastructure 118 _(i). If (at block 620) the data structure 118 _(i) is notin the determined lower level memory device 116 _(j), then the virtualmemory manager 114 copies (at block 622) the data structure 118 _(i)from the lower level memory device 116 _(i) currently having the datastructure 118 _(i) to the lower level memory device 116 _(j) having thedetermined lowest level threshold and removes (at block 624) the datastructure 118 _(i) from the lower level memory device 116 _(i) fromwhich the data structure was copied. If (at block 620) the datastructure 118 _(i) is already in the determined lower level memorydevice 116 _(i) or has been copied there (at block 622), then the devicepointer 212 is updated (at block 626) to indicate the lower level memorydevice 116 _(j) now having the data structure 118 _(i).

With the embodiment of FIG. 6 , an accessed data structure is moved tothe first level memory device 116 ₁ and also retained in a lower levelmemory device that comprises a lower level memory device having anendurance, erasable cycles, commensurate with the access count of thedata structure. By matching the data structure by access count with alower level memory device by endurance, data structures are stored in alower level memory device having an endurance level most appropriate forthe frequency of access of the data structure. Further, if the accesscount of the data structure is higher than the highest level thresholdfor the second memory level device 116 ₂, then the data structure isremoved from the memory level device 116 _(i) having the data structurewithout moving the data structure to another memory level device becausethe access count is too high for lower level memory devices 116 ₂ . . .116 _(n).

FIG. 7 illustrates an embodiment of operations performed by the virtualmemory manager 114 to perform memory management when copies of a datastructure 118 _(i) are maintained in multiple level memory devices 116 ₁. . . 116 _(n). Upon initiating (at block 700) memory management for amultiple copy case, if (at block 702) the amount of free space in thefirst level memory device 116 ₁ is above a memory threshold, thencontrol ends. If (at block 702) the amount of free space is below thememory threshold, then the virtual memory manager 114 selects (at block704) data structures 118 _(i) in the first level memory device 116 ₁indicated as swappable having lowest access counts that satisfy a freespace amount. The operations at blocks 706 through 718 are performed foreach of the selected data structure 118 _(i).

The virtual memory manager 114 determines (at block 708) a lower levelmemory device 116 _(j) having a lowest level threshold exceeding thedata structure 118 _(i) access count, which is the memory device havingan endurance most suited for the access count of the selected datastructure 118 _(i). If (at block 710) the data structure 118 _(i) is notin the determined lower level memory device 116 _(i), then the virtualmemory manager 114 copies (at block 712) the data structure 118 _(i)from the first level memory device 116 ₁ to the lower level memorydevice 116 _(i) having the determined lowest level threshold. If (atblock 710) the data structure 118 _(i) is already in the determinedlower level memory device 116 _(i) or has been copied there (at block712), then the data structure 118 _(i) is removed (at block 714) fromthe first level memory device 116 ₁ and the device pointer 212 isupdated (at block 716) to indicate the lower level memory device 116_(i) now having the data structure 118 _(i).

With the embodiment of FIG. 7 , to free space in the first level memorydevice 116 ₁, the virtual memory manager 114 considers data structureshaving a lowest access count, because such data structures are lesslikely to be updated and accessed and most suitable for storage in alower level memory device 116 ₂ . . . 116 _(n). The selected datastructure having lowest access counts are removed from the first levelmemory device 116 ₁ and retained in a lower level memory device 116 _(i)having a level threshold containing the access count of the datastructure to move.

FIG. 8 illustrates an embodiment of operations performed by the virtualmemory manager 114 to process an access request where multiple copies ofa data structure 118 _(i) are maintained in multiple of the memorydevices 116 ₁ . . . 116 _(n) and there are separate update 206 and read208 counts. Upon processing (at block 800) the access request, if (atblock 802) the accessed data structure 118 _(i) is not swappable 204,control proceeds to FIG. 11 for processing as a non-swappable datastructure. If (at block 802) the swappable flag 204 in the datastructure information 200 _(i) for the accessed data structure 118 _(i)indicates the data structure 118 _(i) is swappable, then the updatecount 206 is incremented (at block 806) if the access is a write and theread count 208 is incremented if the access is a read.

If (at block 808) the accessed data structure 118 _(i) is in the firstlevel memory device 116 ₁, then the access (read or write) is performed(at block 810) at the first level memory device 116 ₁. If (at block 808)the data structure 118 _(i) is not in the first level memory device 116₁, then the virtual memory manager 114 copies (at block 812) the datastructure 118 _(i) from a lower level memory device 116 _(i) to thefirst level memory device 116 ₁ and updates (at block 814) the devicepointer 212 to indicate the first level memory device 116 ₁. If (atblock 816) the access request is an update, then the copies of the datastructures in the first 116 ₁ and lower level memory devices 116 _(i)are updated (at block 818).

If the access is a read (from block 816) or updating the data (fromblock 818), the virtual memory manager 114 determines (at block 820) alower level memory device 116 _(j) having a lowest level thresholdexceeding the data structure 118 _(i) update count 206, which is thememory device having an endurance most suited for the update count ofthe selected data structure 118 _(i). If (at block 822) the datastructure 118 _(i) is not in the determined lower level memory device116 _(i), then the virtual memory manager 114 copies (at block 824) thedata structure 118 _(i) from the lower level memory device 116 _(i)having the data structure 118 _(i) to the lower level memory device 116_(j) having the determined lowest level threshold and the data structure118 _(i) is removed (at block 826) from the lower level memory device116 _(i). Once the data structure is in the determined lower levelmemory device 116 _(j) having the lowest level threshold (from block 822or 826), the device pointer 212 is updated (at block 828) to indicatethe lower level memory device 116 _(j) now having the data structure 118_(i).

With the embodiment of FIG. 8 , an accessed data structure is moved tothe first level memory device 116 ₁ and also retained in a lower levelmemory device that comprises a lower level memory device having anendurance, erasable cycles, commensurate with the update count of thedata structure. By matching the data structure by update count with alower level memory device by endurance, data structures are stored in alower level memory device having a endurance level most appropriate forthe update frequency of the data structure. Further, if the update countof the data structure is higher than the highest level threshold for thesecond memory level device 116 ₂, then the data structure is removedfrom the memory level device 116 _(i) having the data structure withoutmoving the data structure to another memory level device because theupdate count is too high for the endurance profile of the lower levelmemory devices 116 ₂ . . . 116 _(n).

FIG. 9 illustrates an embodiment of operations performed by the virtualmemory manager 114 to perform memory management when copies of a datastructure 118 _(i) are maintained in multiple level memory devices 116 ₁. . . 116 _(n). Upon initiating (at block 900) memory management for amultiple copy case with separate update and read counts, if (at block902) the amount of free space in the first level memory device 116 ₁ isabove a memory threshold, then control ends. If (at block 902) theamount of free space is below the memory threshold, then the virtualmemory manager 114 selects (at block 904) data structures 118 _(i) inthe first level memory device 116 ₁ indicated as swappable having lowestupdate counts 206 that satisfy a free space amount. The operations atblocks 906 through 918 are performed for each of the selected datastructure 118 _(i).

The virtual memory manager 114 determines (at block 908) a lower levelmemory device 116 _(j) having a lowest level threshold exceeding thedata structure 118 _(i) update count 206, which is the memory devicehaving an endurance most suited for the update count of the selecteddata structure 118 _(i). If (at block 910) the data structure 118 _(i)is not in the determined lower level memory device 116 _(j), then thevirtual memory manager 114 copies (at block 912) the data structure 118_(i) from the first level memory device 116 ₁ to the lower level memorydevice 116 _(j) having the determined lowest level threshold. If (atblock 910) the data structure 118 _(i) is already in the determinedlower level memory device 116 _(j) or has been copied there (at block912), then the data structure 118 _(i) is removed (at block 914) fromthe first level memory device 116 ₁ and the device pointer 212 isupdated (at block 916) to indicate the lower level memory device 116_(j) now having the data structure 118 _(i).

With the embodiment of FIG. 9 , to free space in the first level memorydevice 116 ₁, the virtual memory manager 114 considers data structureshaving a lowest update count, because such data structures are lessfrequently updated and most suitable for storage in a lower level memorydevice 116 ₂ . . . 116 _(n). The selected data structures having lowestupdate counts are removed from the first level memory device 116 ₁ andretained in a lower level memory device 116 _(i) having a levelthreshold containing the update count of the data structure to move.

FIG. 10 illustrates an embodiment of operations performed by the virtualmemory manager 114 to generate data structures, such as system type datastructures during system initialization, including data structuresproviding configuration information on logical subsystems, logicalvolumes, path groups, physical paths, logical paths, subsystemcharacteristics, and other configuration data. Upon performing systeminitialization (at block 1000), which may be initiated by a Basic InputOperating System (BIOS), initial microcode load (IML) or other bootdevice, system data structures are generated and stored (at block 1002)in the first level memory device 116 ₁ as part of system initialization.The device pointers 212 in the data structure information 200 _(i) forthe generated system data structures 118 _(i) is updated (at block 1004)to indicate the first level memory device 116 ₁. The virtual memorymanager 114 determines (at block 1006) the data structures 118 _(i)whose data structure information 2001 indicates in field 210 that thedata structures are to be demoted after initialization. The determineddata structures are copied (at block 1008) from the first level memorydevice 116 _(i) to selected lower level memory devices 116 _(i). Theselected lower level memory devices may be selected based on an accesscount or update count to select a lower level memory device having anendurance profile suitable for the access or update count for the datastructure, such as described with respect to FIGS. 7 and 9 .

The copied determined data structures 118 _(i) are removed (at block1010) from the first level memory device 116 ₁ and the device pointers212 for the moved data structures 118 _(i) are updated (at block 1012)to indicate the selected lower memory devices to which they are moved.

With the embodiment of FIG. 10 , data structures that are indicated todemote, which may comprise those system data structures that are veryinfrequently accessed, are moved to a suitable lower level memory device116 _(i) because their infrequent access pattern indicates they will notneed to be stored in the first level memory device 116 ₁ after beinginitialized during system initialization.

FIG. 11 illustrates an embodiment of operations performed by the virtualmemory manager 114 to process accesses to non-swappable data structures118 _(i), such as invoked at blocks 404, 604, and 804 in FIGS. 4, 6, and8 , respectively. Upon initiating (at block 1100) access to anon-swappable data structure 118 _(i), if (at block 1102) thenon-swappable data structure 118 _(i) is not indicated as demote afterinitialization in field 210, then the virtual memory manager 114provides (at block 1104) read or write access to the data structure 118_(i) in the first level memory device 116 ₁. If (at block 1102) the datastructure 118 _(i) is demote after initialization status, then if (atblock 1106) the access is a read, then the virtual memory manager 114provides (at block 1108) read access to the data structure 118 _(i) inthe level memory device 116 _(i) identified by the device pointer 212 inthe data structure information 200 _(i) for the accessed data structure118 _(i).

If (at block 1106) the access is a write and if (at block 1110) theupdate to the data structure 118 _(i) is not a member of a set ofdefined update events, then the requested write is performed (at block1112) at the lower level memory device 116 _(i) indicated in the devicepointer 212 for the data structure 118 _(i). If (at block 1110) theupdate is a member of a set of defined update events, then the virtualmemory manager 114 copies (at block 1114) the data structure 114 _(i)(or specific fields or portions to update) to the first level memorydevice 116 ₁ and updates the device pointer 212 to indicate the firstlevel memory device 116 ₁. Event writes are then performed (at block1116) to the data structure 118 _(i), or specific fields in the datastructure, as part of the event. When the event related writes havecompleted (at block 1118), then the virtual memory manager 114 copies(at block 1120) the updated data structure 118 _(i), or just the updatedfields and portions, from the first level memory device 116 ₁ to aselected lower level memory device 116 _(i)(e.g., lowest level, selectedto reduce wear levelling, etc.), removes the data structure 118 _(i)from first level memory device 116 ₁, and updates the device pointer 212to indicate the selected lower level memory device 116 _(i).

In one embodiment, the defined set of events that triggers moving thedata structure to the first level memory device 116 ₁ may comprise datastructures that are system configuration files very infrequentlyupdated, such as additional or removal of a logical subsystem, volumes,path groups, physical paths, and logical paths. The update events mayalso comprise updating configuration information with new subsystemcharacteristics and other information.

With the operations of FIG. 11 , a data structure 118 _(i) identified asa demote after initialization which is mostly stored in a lower levelmemory device 116 _(i) may be periodically staged into the first levelmemory device 116 ₁ for a burst of writes as part of operations toupdate system configuration files. Because such configuration files arevery infrequently updated, after the update event, the system datastructure may be moved back to a lower level memory device for storageand access. This frees up space in the faster access first level memorydevice 116 ₁ for other more frequently accessed data.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The computational components of FIG. 1 , including the hosts 102 andstorage controller 104, may be implemented in one or more computersystems, such as the computer system 1202 shown in FIG. 12 . Computersystem/server 1202 may be described in the general context of computersystem executable instructions, such as program modules, being executedby a computer system. Generally, program modules may include routines,programs, objects, components, logic, data structures, and so on thatperform particular tasks or implement particular abstract data types.Computer system/server 1202 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 12 , the computer system/server 1202 is shown in theform of a general-purpose computing device. The components of computersystem/server 1202 may include, but are not limited to, one or moreprocessors or processing units 1204, a system memory 1206, and a bus1208 that couples various system components including system memory 1206to processor 1204. Bus 1208 represents one or more of any of severaltypes of bus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, andnot limitation, such architectures include Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 1202 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 1202, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 1206 can include computer system readable media in theform of volatile memory, such as random access memory (RAM) 1210 and/orcache memory 1212. Computer system/server 1202 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 1213 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 1208 by one or more datamedia interfaces. As will be further depicted and described below,memory 1206 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 1214, having a set (at least one) of program modules1216, may be stored in memory 1206 by way of example, and notlimitation, as well as an operating system, one or more applicationprograms, other program modules, and program data. Each of the operatingsystem, one or more application programs, other program modules, andprogram data or some combination thereof, may include an implementationof a networking environment. The components of the computer 1202 may beimplemented as program modules 1216 which generally carry out thefunctions and/or methodologies of embodiments of the invention asdescribed herein. The systems of FIG. 1 may be implemented in one ormore computer systems 1202, where if they are implemented in multiplecomputer systems 1202, then the computer systems may communicate over anetwork.

Computer system/server 1202 may also communicate with one or moreexternal devices 1218 such as a keyboard, a pointing device, a display1220, etc.; one or more devices that enable a user to interact withcomputer system/server 1202; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 1202 to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces 1222. Still yet, computer system/server1202 can communicate with one or more networks such as a local areanetwork (LAN), a general wide area network (WAN), and/or a publicnetwork (e.g., the Internet) via network adapter 1224. As depicted,network adapter 1224 communicates with the other components of computersystem/server 1202 via bus 1208. It should be understood that althoughnot shown, other hardware and/or software components could be used inconjunction with computer system/server 1202. Examples, include, but arenot limited to: microcode, device drivers, redundant processing units,external disk drive arrays, RAID systems, tape drives, and data archivalstorage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims herein after appended.

What is claimed is:
 1. A computer program product for managing data in aplurality of memory devices in a computing system, the computer programproduct comprising a computer readable storage medium having computerreadable program code embodied therein that when executed performsoperations, the operations comprising: indicating data structures todemote as part of system initialization from a first level memory deviceto a second level memory device, wherein the first level memory devicehas lower latency than the second level memory device, wherein the datastructures are identified as having a file name or object name, andcomprise configuration information for the computing system generated byan operating system as part of the system initialization; and as part ofcompleting the system initialization and generating the data structuresin the first level memory device, immediately copying the datastructures indicated to demote as part of the system initialization fromthe first level memory device to the second level memory device andremoving the data structures indicated to demote as part of the systeminitialization from the first level memory device.
 2. The computerprogram product of claim 1, wherein the operations further comprise:receiving a read request to a data structure stored in the second levelmemory device; and returning data to the read request from the datastructure stored in the second level memory device.
 3. The computerprogram product of claim 1, wherein the operations further comprise:maintaining access counts for the data structures stored in the firstlevel memory device that are not indicated to demote as part of systeminitialization, wherein access counts are not maintained for datastructures indicated to demote as part of system initialization.
 4. Thecomputer program product of claim 3, wherein the operations furthercomprise: using the access counts to select data structures to removefrom the first level memory device and retain in the second level memorydevice to free space in the first level memory device; and using theaccess counts to determine whether to remove accessed data structuresfrom the second level memory device.
 5. The computer program product ofclaim 1, wherein the operations further comprise: receiving an update toa data structure indicated to demote as part of system initialization;copying the data structure to update from the second level memory deviceto the first level memory device to update; updating the data structurewith the update; and copying the updated data structure from the firstlevel memory device to the second level memory device and deleting theupdated data structure from the first level memory device.
 6. A computerprogram product for managing data in a plurality of memory devices in acomputing system, the computer program product comprising a computerreadable storage medium having computer readable program code embodiedtherein that when executed performs operations, the operationscomprising: receiving an update to a data structure indicated to demoteas part of system initialization from a first level memory device,wherein the data structure is identified as having a file name or objectname, and comprises configuration information for the computing systemgenerated by an operating system as part of the system initialization,wherein the data structure indicated to demote as part of systeminitialization is immediately demoted from the first level memory devicein response to being generated in the first level memory device as partof the system initialization operations; copying the data structure toupdate from a second level memory device to the first level memorydevice to update, wherein the first level memory device has lowerlatency than the second level memory device; updating the data structurewith the update; and copying the updated data structure from the firstlevel memory device to the second level memory device and deleting theupdated data structure from the first level memory device in response tocompleting updating the data structure.
 7. The computer program productof claim 6, wherein the update to the data structure is to at least onefield in the data structure to update that is less than all the fieldsin the data structure, wherein the copying the data structure comprisescopying only the at least one field to update from the data structure tothe first level memory device, wherein the copying the updated datastructure comprises copying the updated at least one field from thefirst level memory device to the second level memory device and deletingthe updated at least one field from the first level memory device. 8.The computer program product of claim 6, wherein the data structure toupdate is in the second level memory device, wherein the operationsfurther comprise: determining whether the update comprises an updateevent of a plurality of predefined update events; copying the datastructure to update to the first level memory device in response todetermining the update comprises the update event; performing aplurality of writes to the data structure as part of the update event;and copying the data structure updated as part of the update event fromthe first level memory device to the second level memory device anddeleting the updated data structure from the first level memory devicein response to completing the writes for the update event.
 9. Thecomputer program product of claim 8, wherein the predefined updateevents comprise a plurality of update events that are a member of asubset of update events comprising additional or removal of a logicaldevice in the computing system; a volume in the computing system; pathgroups; physical paths; logical paths; and subsystem characteristics andother configuration changes.
 10. The computer program product of claim8, wherein the operations further comprise: performing the update to thedata structure to update in the second level memory device in responseto determining that the update does not comprise one of the plurality ofpredefined update events.
 11. A system, comprising: a first level memorydevice; a second level memory device; a virtual memory manager toperform: indicating data structures to demote as part of systeminitialization from a first level memory device to a second level memorydevice, wherein the first level memory device has lower latency than thesecond level memory device, wherein the data structures are identifiedas having a file name or object name, and comprise configurationinformation for the system generated by an operating system as part ofthe system initialization; and as part of completing the systeminitialization and generating the data structures in the first levelmemory device, immediately copying the data structures indicated todemote as part of system initialization from the first level memorydevice to the second level memory device and removing the datastructures indicated to demote as part of system initialization from thefirst level memory device.
 12. The system of claim 11, wherein theoperations further comprise: receiving a read request to a datastructure stored in the second level memory device; and returning datato the read request from the data structure stored in the second levelmemory device.
 13. The system of claim 11, wherein the operationsfurther comprise: maintaining access counts for the data structuresstored in the first level memory device that are not indicated to demoteas part of system initialization, wherein access counts are notmaintained for data structures indicated to demote as part of systeminitialization.
 14. The system of claim 13, wherein the operationsfurther comprise: using the access counts to select data structures toremove from the first level memory device and retain in the second levelmemory device to free space in the first level memory device; and usingthe access counts to determine whether to remove accessed datastructures from the second level memory device.
 15. The system of claim11, wherein the operations further comprise: receiving an update to adata structure indicated to demote as part of system initialization;copying the data structure to update from the second level memory deviceto the first level memory device to update; updating the data structurewith the update; and copying the updated data structure from the firstlevel memory device to the second level memory device and deleting theupdated data structure from the first level memory device.
 16. A system,comprising: a first level memory device; a second level memory device; avirtual memory manager to perform: receiving an update to a datastructure indicated to demote as part of system initialization from afirst level memory device, wherein the data structure is identified ashaving a file name or object name, and comprises configurationinformation for the system generated by an operating system as part ofthe system initialization, wherein the data structure indicated todemote as part of system initialization is immediately demoted from thefirst level memory device in response to being generated in the firstlevel memory device as part of the system initialization operations;copying the data structure to update from the second level memory deviceto the first level memory device to update, wherein the first levelmemory device has lower latency than the second level memory device;updating the data structure with the update; and copying the updateddata structure from the first level memory device to the second levelmemory device and deleting the updated data structure from the firstlevel memory device in response to updating the data structure.
 17. Thesystem of claim 16, wherein the update to the data structure is to atleast one field in the data structure to update that is less than allthe fields in the data structure, wherein the copying the data structurecomprises copying only the at least one fields to update from the datastructure to the first level memory device, wherein the copying theupdated data structure comprises copying the updated at least one fieldfrom the first level memory device to the second level memory device anddeleting the updated at least one field from the first level memorydevice.
 18. The system of claim 16, wherein the data structure to updateis in the second level memory device, wherein the virtual memory managerfurther performs: determining whether the update comprises an updateevent of a plurality of predefined update events; copying the datastructure to update to the first level memory device in response todetermining the update comprises the update event; performing aplurality of writes to the data structure as part of the update event;and copying the data structure updated as part of the update event fromthe first level memory device to the second level memory device anddeleting the updated data structure from the first level memory devicein response to completing the writes for the update event.
 19. Thesystem of claim 18, wherein the predefined update events comprise aplurality of update events that are a member of a subset of updateevents comprising additional or removal of a logical device in thesystem; a volume in the system; path groups; physical paths; logicalpaths; and subsystem characteristics and other configuration changes.20. The system of claim 18, wherein the virtual memory manager furtherperforms: performing the update to the data structure to update in thesecond level memory device in response to determining that the updatedoes not comprise one of the plurality of predefined update events. 21.A method for managing data in a plurality of memory devices in acomputing system, comprising: indicating data structures to demote aspart of system initialization from a first level memory device to asecond level memory device, wherein the first level memory device haslower latency than the second level memory device, wherein the datastructures are identified as having a file name or object name, andcomprise configuration information for the computing system generated byan operating system as part of the system initialization; and as part ofcompleting the system initialization and generating the data structuresin the first level memory device, immediately copying the datastructures indicated to demote as part of system initialization from thefirst level memory device to the second level memory device and removingthe data structures indicated to demote as part of system initializationfrom the first level memory device.
 22. The method of claim 21, furthercomprising: receiving a read request to a data structure stored in thesecond level memory device; and returning data to the read request fromthe data structure stored in the second level memory device.
 23. Themethod of claim 21, further comprising: maintaining access counts forthe data structures stored in the first level memory device that are notindicated to demote as part of system initialization, wherein accesscounts are not maintained for data structures indicated to demote aspart of system initialization.
 24. The method of claim 23, furthercomprising: using the access counts to select data structures to removefrom the first level memory device and retain in the second level memorydevice to free space in the first level memory device; and using theaccess counts to determine whether to remove accessed data structuresfrom the second level memory device.
 25. The method of claim 23, furthercomprising: receiving an update to a data structure indicated to demoteas part of system initialization; copying the data structure to updatefrom the second level memory device to the first level memory device toupdate; updating the data structure with the update; and copying theupdated data structure from the first level memory device to the secondlevel memory device and deleting the updated data structure from thefirst level memory device.